Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not complete but enough to review as part 1 😄
OpenTelemetry.AutoInstrumentation
namedElastic.OpenTelemetry.AutoInstrumentation
.Through a bit of msbuild magic we redistribute
instrument.{sh|cmd}
as_instrument.{sh|cmd}
and introduce our owninstrument.{sh|cmd}
that sets the appropiate plugin environment variable before calling the opentelemetry instrument script.This allows the invocation to be exactly the same no matter if our distribution or the vanilla opentelemetry package is installed. A user can move from or away from Elastic without having to touch orchestration work. Simply installing the package is enough to move to or away from us.
./build.sh redistribute
build command that redistributes the opentelemetry autoinstrumentation zip files that include our AutoInstrumentation plugin.A follow up of this PR will focus on creating Elastic versions of the global auto instrumentation installation scripts and ensuring these get staged as part of the release.